Skip to content

Investigating the Drone timeout issue#16671

Draft
PhilLab wants to merge 1 commit intomasterfrom
ph/fix_drone_ci_timeout
Draft

Investigating the Drone timeout issue#16671
PhilLab wants to merge 1 commit intomasterfrom
ph/fix_drone_ci_timeout

Conversation

@PhilLab
Copy link
Contributor

@PhilLab PhilLab commented Mar 12, 2026 •
edited
Loading

Notes

  • No timestamp printing needed. The Drone log UI shows the elapsed seconds on the right, when opening full screen.
  • Looking at the prior MR's drone run of test-stable: https://drone.nextcloud.com/nextcloud/android/28763/1/3
    • assembleGplayDebugAndroidTest: 7.5 minutes
    • waiting for Emulator: 5 seconds
    • installGplayDebugAndroidTest: 26 second
    • waiting for server & deleting old Github comments: 10 seconds
    • createGplayDebugCoverageReport (configuring the tasks): 2 minutes
    • createGplayDebugCoverageReport (actually running the tests): ? - timeout
      • After task configuration, the actual test runs in the logs are only spanning 24 minutes.
    • the last log line android(AVD) - 16 Tests 417/569 completed. (0 skipped) (0 failed) appears at second 2058 (34 minutes total time). This is shorter than the stated overall time of 60 minutes.
    • So either there is something crashing so hard that the job dangles until timeout. Or the job is stopped too early.
    • The parallel server job's last log line is also at around 34 minutes
  • Looking at this MR's drone run https://drone.nextcloud.com/nextcloud/android/28833/1/3
    • the last log line android(AVD) - 16 Tests 439/595 completed. (0 skipped) (7 failed) appears at second 2973 seconds (49 minutes total time).

🖼️ Screenshots

🏚️ Before 🏡 After
B A

🏁 Checklist

  • Tests written, or not not needed

@PhilLab PhilLab changed the title Investingating the Drone timeout issue#16670 Investingating the Drone timeout issue Mar 12, 2026
@PhilLab
Extend Drone timeout to 90 minutes
e121293 
There are quite a lot of instrumented tests (569 at the moment), so we
need to give them more time to run through.

Signed-off-by: Philipp Hasper <vcs@hasper.info>
@PhilLab PhilLab force-pushed the ph/fix_drone_ci_timeout branch from b04508e to e121293 Compare March 13, 2026 16:40
@PhilLab
Copy link
Contributor Author

PhilLab commented Mar 13, 2026

@alperozturk96 I am trying to experiment with the Drone runs. Extending the timeout apparently requires an approval in the Drone UI, as I changed the .drone.yml file. For security purposes.

I don't have the permission to approve this change - so can you take a look?
image

@PhilLab PhilLab changed the title Investingating the Drone timeout issue Investigating the Drone timeout issue Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@PhilLab